Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

gsc_manager_type table — gscmt

This table contains the definition of the standard Progress Dynamics managers.

Table 13–5 lists the table’s FLA, fields, and foreign keys.

Table 13–5: gsc_manager_type table information 

Table FLA	Fields (data type)	Foreign keys
gscmt	manager_type_obj (Decimal) manager_type_code (Character) manager_type_name (Character) system_owned (Logical) write_to_config (Logical) static_handle (Character) manager_narration (Character) db_bound_smartobject_obj (Decimal) db_unbound_smartobject_obj (Decimal)	manager_type_obj

Table 13–6 gives details of the table’s indexes.

Table 13–6: gsc_manager_type index information 

Index name	Elements	Type
XPKgsc_manager_type	manager_type_obj	Primary Unique
XAK1gsc_manager_type	manager_type_code	Unique
XIE1gsc_manager_type	manager_type_name	Nonunique
XIE2gsc_manager_type	db_bound_smartobject_obj	Nonunique
XIE3gsc_manager_type	db_unbound_smartobject_obj	Nonunique

A predefined set of managers that support the framework functionality exists in this table. Only managers that directly affect the core functionality of the Progress Dynamics framework must be defined as manager types. For example, because no other code can be started without the Session Manager, the Session Manager must be listed.

The physical procedures to run for a manager type are defined in this table. Two standard physical procedures are supported:

The bound manager object is for sessions that have a database connection service type as one of its session services. A manager of this type requires a database connection and communicates directly with schema tables.
The unbound manager object is for sessions that do not have a database connection. A manager of this type does not require a database connection and communicates indirectly with schema tables through a bound manager object running on the server in a session with a database connection.

To support overrides of standard manager functionality, the super procedure attribute can be used against the manager object to define a super procedure stack of override functionality. It would point at a specific procedure to add as a super procedure, which in turn could have a super procedure, and so on.

The bound and unbound manager fields might need to be customized to point at the last procedure in the super procedure stack. To ensure that the customizations do not get lost, these fields must be defined as fields that are not overridden by new deployments. This is defined in the exclude_fields field of the gsc_dataset_entity table.

The manager objects specified here are always started for any session type that includes the manager type as a required manager type on the gsm_required_manager table. Because of this approach, different manager objects cannot be started for different session types. If this is required, then different manager types must be defined.